Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-60349 | F5BI-LT-000203 | SV-74779r1_rule | Medium |
Description |
---|
Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). The intent of this requirement is to require support for a secondary certificate validation method using a locally cached Certificate Revocation List (CRL) in case access to OCSP (required by CCI-000185) is not available. This requirement applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management). |
STIG | Date |
---|---|
F5 BIG-IP Local Traffic Manager 11.x Security Technical Implementation Guide | 2015-06-02 |
Check Text ( C-61271r1_chk ) |
---|
If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable. When user authentication intermediary services are provided, verify the BIG-IP Core is configured to implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> SSL >> Client. Select an SSL client profile that is used for client authentication with Virtual Server(s). Review the configuration under the "Client Authentication" section. Verify that "Client Certificate" is set to "require" or "request". Verify that "Certificate Revocation List (CRL)" is set to a local CRL filename. If the BIG-IP Core is not configured to implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network, this is a finding. |
Fix Text (F-65963r1_fix) |
---|
If user access control intermediary services are provided, configure the BIG-IP Core is configured to implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. |